Magnum One/Magnum One (Mid-American Digital) (Disc Manufacturing).iso/d2/novdos50.arc/README.TXT

Text File | 1991-04-28 | 17KB | 389 lines

  UPGRADING NETWORKS FOR IBM PC DOS VERSION 5.0

    If you use an IBM or Novell network, you might need to upgrade one or more
    files on your hard disk before you install IBM PC DOS version 5.0
    on your computer.

    IBM PC DOS version 5.0 provides new versions of one or more network files
    for those networks.  To run these networks with IBM PC DOS version 5.0,
    install the appropriate file on your hard disk. The files that are provided
    by this IBM PC DOS 5.0 upgrade are interim fixes for compatibility with DOS 5.0
    only. They do NOT contain any of the fixes for problems other than DOS 5.0
    compatibility. For a complete update of your network files, please
    contact normal channels for those upgrades or your vendor representative.

    For any problems encountered during the upgrade process, contact your IBM
    support channel or your point of sale. For any problems associated with the
    network itself please contact your normal support channel or your vendor
    representative.

    For networks other than IBM or Novell, please contact your normal upgrade
    channel or your vendor representative for any questions or upgrades for
    DOS 5.0 compatibility.

    This file describes how to update files for IBM and Novell networks and
    provides other important information about these networks.  Make sure
    you read and follow any instructions for your network before you use it
    with IBM PC DOS version 5.0.  Check with your system administrator before
    performing the instructions in this chapter.  Your system administrator
    might have instructions specific to your work environment.

  IMPORTANT:  UPGRADE THE NETWORK FILES ON YOUR COMPUTER BEFORE YOU RUN THE
  NETWORK WITH IBM PC DOS VERSION 5.0.

    In general, if you are using a network, do the following:

    Follow the instructions in the appropriate section to upgrade your
    network files.

    You need to be familiar with the following concepts to successfully
    complete the instructions in this chapter:

     - Using DOS to change drives and directories
     - Connecting to a network
     - Searching a disk for a file
     - Searching a file for text
     - Editing a text file

    For more information about the preceding tasks, see the IBM PC DOS
    version 5.0 User's Guide and Reference.

    For more information about the IBM PCLP and DLR networks, see the
    IBM PC Network Disk readme file.

  UPGRADING THE NOVELL NETWORK

  This compatibiity upgrade applies to Novell Netware 2.1 and above.

    The NetWare workstation shell is Novell's basic DOS
    shell.  You may require a different shell for a specific
    application.  Contact your local authorized Novell reseller
    if you believe another is needed.

    1. Using PC-DOS on a Novell NetWare network will require
       you to update your NETx.COM, EMSNETx.EXE, or XMSNETx.EXE
       with the NET5.COM, XMSNET5.EXE, or EMSNET5.EXE.

       For example, if you are using NET4.COM, replace your NET4.COM
       file with the NET5.COM file found on the diskette.

    2. Included on this diskette is an IPX.OBJ v3.02.  You may want to
       update your IPX.COM file to this version.  In order to update,
       you will need to run the NetWare utility SHGEN or WSGEN.
       For more information on using these utilities check your
       NetWare documentation.

       To check your IPX version (IPX allows the NetWare shell to
       communicate with a NetWare file server) type at the command line
       where you start NetWare

             IPX I <Enter>

    3. To allow workstations to remote program load properly with PC-DOS 5.x
       the RPLFIX.COM file is required.  Instructions for using RPLFIX.COM
       are listed below.

    4. If you experience problems switching between IPX-specific programs
       (such as SYSCON, and RCONSOLE or other third party products),
       you may need to use TBMI2.COM.  TBMI2 allows switching between
       peer-to-peer applications that run under NetWare with a multitasking
       environment such as PC-DOS 5.0.  Instructions for using TBMI2.COM
       are listed below.

    5. If you are using the NetWare utilities MAP, LOGIN, and SESSION
       from more than one command prompt via the DOS 5.0 Task Swapper,
       the resulting drive mappings may not work as expected.  It is best
       to map drives globally with these utilities before entering the
       DOS Shell and using the Task Swapper.

    6. If you are running a Novell network and you set the COMSPEC variable
       after starting PC-DOS 5.0, either remove the C:\dos\ entry from
       the SHELL= command in your CONFIG.SYS file or contact your Novell
       vendor to get a LOGIN program (version 3.58 dated 2-08-91).


    Installing RPLFIX.COM
    RPLFIX is used to allow workstations to remote program load (RPL) properly
    with DOS 5.x and above.  It must be run after the boot image file
    (usually NET$DOS.SYS) has been created using the DOSGEN utility.  RPLFIX
    will modify the boot image file.  RPLFIX needs to be run against the boot
    image file once.  The utility will detect attempts to run RPLFIX against
    an already modified boot image file, and will make no further modifications.

    Follow the instructions for DOSGEN (setting up remote reset workstations)
    in the Novell reference manuals.  After performing all steps as outlined in
    the manual to create the boot image file, run RPLFIX.COM.

    The remote workstation may hang during the reset process if you are
    resetting using DOS 5.x or above and the boot image file has not been
    modified by RPLFIX.


    RPLFIX can be found on this Network diskette.  After you have located
    RPLFIX.CO a drive to the LOGIN subdirectory on the file server you wish
    to remote reset from.  The DOSGEN procedure instructed you to create a
    boot image file in that subdirectory (usually named NET$DOS.SYS). If the
    drive you mapped to SYS:LOGIN was drive F, then you would enter the
    following:

       RPLFIX F:NET$DOS.SYS <ENTER>

    RPLFIX needs to be run if the version of DOS loaded on the floppy disk
    used with DOSGEN is 5.x or greater.  Earlier versions of DOS do not require
    that this utility be run.

 NOTE:  If you renamed your boot image file, then you must use the new filename
        with RPLFIX:

           RPLFIX [d:]<boot image file> <ENTER>

       [d:] is the drive letter where the image file is located
       <boot image file> is the name of the file created with the DOSGEN utilit


  Installing TASK-SWITCHED BUFFER MANAGER V2.0

    The Task-Switched Buffer Manager v2.0 for IPX/SPX
    (TBMI2) is a program used with multitasking environments
    to allow switching between peer-to-peer applications.
    The NetWare program file TBMI2.COM should be used when a
    DOS application that makes direct calls to IPX or SPX
    (called a peer-to-peer application) is run under NetWare
    with a multitasking environment (such as DOS v5.0).

    The DOS v5.0 DOSSHELL environment in real and standard modes
    allows application task switching (sometimes called swapping).
    Each application runs in a separate DOS session (sometimes
    called DOS Prompt) in 640K of memory. Part of this memory,
    called global memory, contains drivers and TSRs such as
    COMMAND.COM and, if you are running NetWare, IPX.COM and
    NETx.COM. The other part of memory, called local memory,
    contains the application and application data.

    DOS v5.0 DOSSHELL switches from one DOS application to another
    by moving the contents of the current DOS session from
    conventional memory to disk, and then loading the contents
    of the new DOS session into conventional memory. Only the
    local memory is switched; the global memory with its drivers
    and TSRs stays intact and is used with the new session.
    This means that separate local memory segments exist, one for
    each DOS session, while only one global memory segment exists.

    Most DOS applications under NetWare with DOS v5.0 DOSSHELL
    call the network by making a DOS call from local memory
    (where the application resides) to the network shell
    (NETx) in global memory, which passes the call to IPX
    or SPX, which then passes the call to the network. This
    type of application has no need for the task-switched
    buffer manager, because the passing of calls from local
    to global memory occurs between the application and
    the shell.

    When an IPX-accessing application (in local memory)
    wants to communicate directly with the network, it makes
    a call directly to IPX or SPX (in global memory), bypassing
    the shell. IPX or SPX then passes the call on to the network.
    If the application is switched, IPX or SPX will lose
    contact with the application, being unable to use the
    program's data. This type of application must have the
    task-switched buffer manager if it is to be used in a
    switching environment such as the DOS v5.0 DOSSHELL.

    With the task-switched buffer manager, the application
    (in local memory) calls IPX, but the call is intercepted
    by the task-switched buffer manager (in global memory),
    which passes the call to IPX or SPX and then to the network.
    TBMI2 maintains a buffer in global memory to hold calls
    received from the various local segments, and then remaps
    this buffer to the various sessions as they are switched.
    TBMI2 (in global memory) also receives ID information from
    the DOS v5.0 DOSSHELL so that it knows which session it is
    receiving calls from.  Without TBMI2 the application cannot
    be switched without risk of failure.

    There is no need for TBMI2 in DOS sessions if you will not
    be switching between sessions. You also do not need TBMI2
    if your applications do not communicate directly with IPX.
    If you are not sure that your applications make direct
    calls to IPX, go ahead and run TBMI2; it will not affect
    operations in any way other than use a small amount of
    memory. After running the application for a period of
    time, enter the command TBMI2 /D and look at the value
    associated with the field Far Call Usage. This value
    specifies how many times TBMI2 has actually made calls.
    If this value is zero, then your application is not
    using TBMI2; you can safely run your application in the
    future without TBMI2.

  NOTE:  You must update to IPX v3.02 before you can use
         TBMI2.


  TBMI2.COM

    This program provides the data buffers needed to
    virtualize the IPX and SPX requests made from applications
    running in a DOS session. Because these buffers need to
    be allocated before the DOS v5.0 DOSSHELL starts, TBMI2
    must be run before starting the DOSSHELL.

  The following are valid command line parameters:

   /? or /H       Display help or usage information.

   /C=<filename>  Load TBMI2 using this configuration file.
                  For example, enter "TBMI2 /C=TBMI2.CFG"
                  on the command line.

   /D             Display diagnostic information and
                  current allocation limits.

   /I             Display version information.

   /U             Unload TBMI2 from memory after exiting
                  Windows.

    This program reads configuration information from a
    configuration file in the current directory. One parameter
    is entered on each line in the configuration file. This
    file's name is NET.CFG by default; a different name can
    be specified using the /C= parameter on the command line.

   The following are valid configuration file parameters:

  INT 64    This is similar to the IPX configuration
            parameter; it specifies that TBMI2 should
            support interrupt 64h IPX and SPX calls.
            This should be set to either OFF or ON. For
            example, enter the line "INT 64 = ON" in
            the configuration file. The default is ON
            for maximum compatibility.

  INT 7A    This is similar to the IPX configuration
            parameter; it specifies that TBMI2 should
            support interrupt 7Ah IPX and SPX calls.
            This should be set to either OFF or ON. For
            example, enter the line "INT 7A = ON" in the
            configuration file. The default is ON for
            maximum compatibility.

  ECB COUNT This specifies how many nondata event control
            blocks (ECBs) will be allocated for use by DOS
            programs needing virtualization. These ECBs
            apply to most AES events. If TBMI2 runs out of
            nondata ECBs, data ECBs can be allocated for use.
            If no ECB can be allocated from TBMI2's pool of
            ECBs, a failure will result with a completion
            code of FEh (or -2).

            The minimum allowed value for this parameter is 10,
            the maximum is 255, and the default is 20. For
            example, enter the line "ECB COUNT = 20" in the
            configuration file. Each allocated ECB requires
            52 bytes of memory; the 20 ECB default will
            require 1040 bytes. The maximum allocation also
            depends upon available memory, and the total size
            of all ECBs must be less than 64K, which will
            normally limit the ECB count to less than 255.
            Use the /D command line parameter to verify
            actual allocations.

  DATA ECB
  COUNT     This specifies how many data ECBs will be
            allocated for use by DOS programs needing
            virtualization. These ECBs apply to most IPX
            and SPX send-and-receive packets. If a nondata
            ECB request is made when none are available, a
            data ECB will be used. If no ECBs are available
            from TBMI2's pool of ECBs, a failure will result
            with a completion code of FEh (or -2).

            The minimum allowed value for this parameter is 10,
            and the default is 60. The theoretical maximum is 255,
            but 89 is the practical limit. For example, enter the
            line "DATA ECB COUNT = 60" in the configuration file.
            Each allocated data ECB requires 628 bytes of memory;
            the 60 ECB default will require 37680 bytes.  The
            maximum allocation also depends upon available memory,
            and the total size of all ECBs must be less than 64K,
            which will normally limit the data ECB count to less
            than 255. Use the /D command line parameter to
            verify actual allocations.


  TBMI2 Usage

    Do the following to start TBMI2:

     1. Start TBMI2 by entering the command "TBMI2" on the
        command line, followed by optional command line
        parameters listed above.

     2. Start the DOSSHELL program normally.

    TBMI2 could be included in a batch file starting DOSSHELL
    to ensure that it is always started before DOSSHELL and
    unloaded afterwards. For example, the batch file could
    include the following:

     TBMI2
     DOSSHELL
     TBMI2 /U

   TROUBLESHOOTING


   TBMI2

    If while using TBMI2 you encounter problems, you may need
    to troubleshoot the TBMI2 configuration. Use the /D option
    with TBMI2 to display diagnostic information and the current
    allocation limits.

    Check the values associated with "Max Buffers Used," which
    tells you how many buffers are used, and "Configured Data
    ECBs," which tells you how many are available. If the number
    of buffers used approaches or equals the number of buffers
    available, then you should increase the number of buffers
    available using the ECB COUNT and DATA ECB COUNT parameters
    in the configuration file.

    If the "Unavail buffer count" is ever more than zero, you
    should also increase the number of buffers available using
    the ECB COUNT and DATA ECB COUNT parameters in the
    configuration file.

    The COMCHECK and RCONSOLE utilities are known to use too
    many buffers and cannot be used with TBMI2.

    For more information about using read-only files see the IBM PC DOS
    version 5.0 User's Guide and Reference.

  MEMORY CONFLICTS WITH NETWORK ADAPTER CARDS

    If you are using EMM386.EXE to provide either expanded memory (EMS) or
    access to reserved memory (also known as upper-memory blocks or UMBs)
    and you experience problems with your network, exclude the memory
    address of your network adapter card.

    To exclude a memory address in EMM386.EXE, use the
    x=<memory-address-range> switch with the DEVICE command.

    For more information about this switch, see the IBM PC DOS verson 5.0
    User's Guide and Reference.

    Some common memory address ranges are:

    C000-C7FF
    C800-CFFF
    D000-D7FF
    D800-DFFF

    To determine the memory address range to exclude, see the documentation
    that came with your network adapter card.